In this episode, Dave and Jamison answer these questions:

1. Dear Damison and Javison, I work at a very small startup (<10 engineers) and am trying to hire 2 engineers. I’m doing the intro/screener interview for these roles & am working with a recruiting firm to source candidates. My problem is that sometimes my intuition tells me that a candidate is not going to make it through our hiring process, but I can’t articulate why. Our hiring process is neither cruel nor unusual, and on paper these candidates have the skills and experience we’re looking for. But I feel a duty to let the hiring process do its work; I want to be principled about this. For reference, I’d say I screen out 2/3 of recruiter-screened candidates, and of those remaining, 2/5 of the candidates have the je ne sais quoi for which I should be saying non, merci. One made it all the way to reference checks! Do I need to do a better job rejecting these nice, smart people instead of wasting our time? Also note that I am not a manager, and although I have a lot of experience interviewing candidates, this is the first time I’ve done the *first* interview with candidates (first-ish; the recruiting firm interviews them first).

2. Listener Jeppe says,

   Hi Soft Skills nation,

   What’s the accepted practice with staying or leaving the private chat channels of my previous team?

   I work at a large company and recent switched teams internally. I helped establish the team and got along really well with them. The transfer was on good terms (they invited to their Christmas dinner after the transfer!) and my managers agreed that I could always help my old team in case something came up.

   I’m still in the internal chat channels for my old team. I love hearing what they’re up to and catching up. They explicitly told me not to be a stranger, so I’m not! However, I don’t think there’s much business value in being in their channels. Sometimes we have more technical chats about internal tools, and it would probably be better if I had those discussion with my new team.

   What should I do? Should I just stay until their manager decides to kick me out? Should I be proactive and talk with the manager about it? Should I leave a teary message about how I’m going to miss them all (even if I see them regularly at lunch and outside work sometimes)?

In this episode, Dave and Jamison answer these questions:

1. Hey Guys, long time listener, first time asker!

   At my BigCorp Co., whenever I talk to my skip level about my concerns, it seems we are playing the ‘Gloom Olympics’ every time we meet. I’ll mention I worked late, and he’ll counter with, ‘That’s nothing, I haven’t slept in three days!’

   This repeated lack of empathy is demotivating and I don’t think I have had a fruitful discussion with him.

   How can I tackle this? How can I feel heard?

2. I’ve decided to leave my current job as a software engineer at a large retail chain. This is my first out of university, and I’ve been here three years.

   I’m interviewing for two other jobs: one as an engineer at another large retail chain on a team, and another at a world renowned European football club.

   That job would be very different. I’d be the first internal dev hire ever, and I was told I should expect no other devs to get hired for 2+ years. I’d write my own tickets and review my own prs. The project would be to build a dashboard to manage the players - drug testing, injuries, rosters - internally.

   What should I do? Feedback & mentorship were central to my growth at my current job. I won’t have that at the sports club. My concern is I go to the football team, drink a lot of beer & have a great time, but after 3 years of being my own boss, I’ll think I’m the greatest dev ever but really not have kept up to date with modern trends, forgotten how to take feedback, and written a lot of 💩 code.

In this episode, Dave and Jamison answer these questions:

1. Listener AWS multi-region is not real multi-region, ask me how I know asks,

   We’ve recently acquired some bright-eyed and bushy-tailed new grads. What have you found to be the most effective way to onboard new grads into development roles? How has it changed (if at all) since the advent of LLMs? I want to make sure my new-grad crushing machine is operating as smoothly as possible considering the recent advancements in developer tooling. Those new grads won’t crush themselves!

2. Listener Taso asks,

   Early in my career I was all-in on startups. Then I spent seven years in big companies in leadership roles. I learned a lot, but the politics and the pace were so slow that at some point I’m pretty sure geological processes were moving faster than our release cycles. So I finally flipped some metaphorical fingers and quit. Since then I’ve been interviewing almost exclusively with startups… except Google, where I somehow ended up with an offer on a team I’d genuinely enjoy. You’ve both bounced between big tech and startups—if you were in my shoes, how would you think about choosing between the two?